Swisscom Cloud Services Connectivity (SCSC)
In a nutshell: Your DDCs are linked with the chosen connectivity service (e.g. BNS) via connection points (CP) on both sides (DDC and connectivity service). For doing that, you first configure CP's on both sides and link those CPs together. After doing that, they establish automatically a logical connection (LC). Over this LC, traffic is flowing between your DDC and the configured connectivity service. The traffic structure itself is called service connect (SC).
Connection point (CP)
Preparations before creating a CP
- Being clear about your WAN network concept
- CP visibility: shall the CP be usable from only one DDC or over all DDC's ?
- WAN interconnection provider credentials (e.g. BNS)
- Network settings: the network settings need to correlate with you WAN connectivity. Otherwise there is a risk of loosing connectivity
- Shared: when choosing shared, you may access the CP (the EON) within all of your DDCs. This visibility cannot be limited to specific DDC's
- Connectivity service credentials (e.g. for BNS) should be kept ready, as they will be requiered for CP configuration
Connection point types
The following connection point topology types are available. They influence the way, the logical connection(s) transfer the ip traffic between linked connection points. Please contact our dcs professional services team in case you are unsure about the correct setting.
Endpoint (Any to Any)
The "Any to any" topology (default type) allows the communication between networks situated behind the VRFs. Furthermore, the IP routing exchange is allowed between all connected VRFs and connection points (A,B,C). You will most likely this type of CP for you applications like BNS.
"Extranet hub" allows the control of IP routing exchange between the connection points. In the example above, routes between A,B,C are only learned over E.